home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 1
/
Cream of the Crop 1.iso
/
PRINTER
/
CVR140.ARJ
/
READ.ME
< prev
next >
Wrap
Text File
|
1991-09-09
|
13KB
|
272 lines
CVR - The Disk Cover Utility
Version 1.40 - (C)Copyright Larry J. Bristol 1990-1991
***********************************************************************
*************** Distribution Files ************************************
***********************************************************************
You should have received the following files from the distribution of
the CVR program:
CVR.DOC ------ how to use and customize CVR
CVR.EXE ------ the executable program
CONFIG.BAT --- customization procedure
READ.ME ------ you are reading it now
REGISTER.DOC - license registration order form
You should have received the following printer configuration files:
AUTHORS.CFG -- My personal configuration (Epson LQ-510)
EPSONFX.CFG -- Epson FX series
EPSONLQ.CFG -- Epson LQ series
IBMGRAPH.CFG - IBM Graphics (5151)
LASJET1P.CFG - HP LaserJet series
LASJET2P.CFG - HP LaserJet IIP series
OKI9293.CFG -- OkiData Microline 92/92 (without Plug'N Play)
PANSONIC.CFG - Panasonic KX-P1180/P1124 printers
You should have received the following customization script files,
which correspond to the prepared configuration files above:
AUTHORS.SCR
EPSONFX.SCR
EPSONLQ.SCR
IBMGRAPH.SCR
LASJET1P.SCR
LASJET2P.SCR
OKI9293.SCR
PANSONIC.SCR
In addition, you should have the following sample customization script
files:
DRIVES.SCR --- Change drive configuration script sample
PRTNAME.SCR -- Change printer device name script sample
EXAMPLE.SCR -- Complete configuration script example
***********************************************************************
*************** Self-Test Virus Protection ****************************
***********************************************************************
The CVR program performs a complete self-test every time it is run to
detect any form of modification such as an infection by a computer
virus. If any modification is detected, the program will display the
following message and refuse to execute any further:
Program integrity has been compromised.
If you should suddenly start receiving this message and you cannot
account for any modifications to the program files, it is a strong
possibility that your system may be infected by a virus. You should
perform an integrity check of your entire computer system to look for
other programs infected by a virus.
Note that ANY modification of the CVR program files will result in this
condition. This means that program file compression facilities (such
as PKLITE) cannot be used on the CVR program files. In order to
execute the CVR program, you will have to install a new, unmodified
copy.
***********************************************************************
*************** Evaluation Period *************************************
***********************************************************************
During your evaluation of the CVR program (prior to the entry of a
valid license registration ID), there are a few special restrictions on
the CVR program. These restrictions do not apply to a licensed copy of
the program.
Unlicensed copies of the CVR program may be used for evaluation
purposes for a maximum of 30 days. This 30 day evaluation period
begins when the CVR program is executed for the first time on your
computer. Each time it is run, CVR will tell you how many days remain
in the evaluation period. Once this period has expired, the program
will no longer execute.
The program execution file (CVR.EXE) and configuration file (CVR.CFG)
must not be given the "read-only" or "system" file attributes, and they
must not placed on a write-protected disk. One of the following error
messages may result, and the program will refuse to execute:
Program integrity has been compromised.
Error opening program file "-filename-".
Error closing program file "-filename-".
The system clock must be set to the correct date and time. If not set
properly, CVR will display the following error message and will refuse
to execute:
You must set your system clock properly.
The CVR program performs a complete self-test every time it is run, to
detect any form of modification. For non-licensed copies of the
program, a few extra tests are performed to detect tampering with the
mechanisms used to limit the length of the software evaluation period.
If tampering is detected, the following error message will result, and
the program will refuse to execute:
Program integrity has been compromised.
***********************************************************************
*************** Customization Addresses *******************************
***********************************************************************
The offsets (as used by DEBUG) of the customization areas within the
CVR configuration file (CVR.CFG) are as follows:
0120 - default diskette drive ID
0121 - default for sort/nosort
0128 - diskette drive configuration table
0130 - name of the print output device
0200 - Initialize printer string
0220 - Reset printer string
0240 - Form feed string
0250 - SET to 8 lines/inch string
0260 - RESET from 8 lines/inch string
0270 - SET to condensed mode string
0280 - RESET from condensed mode string
0290 - SET to double wide characters string
02A0 - RESET from double wide characters string
02B0 - SET to emphasized mode string
02C0 - RESET from emphasized mode string
02D0 - SET to underlined mode string
02E0 - RESET from underlined mode string
***********************************************************************
*************** Thoughts on Customization *****************************
***********************************************************************
You may need to "fiddle" with the print code strings in order to get
them to work exactly the way you like. Experimentation might be the
order of the day. Note that I do not have the opportunity to test all
of the script files personally - please let me know if there you
encounter a problem.
A lot of the programming in CVR is to make sure that the columns and
borders are aligned. The program assumes that the printer code strings
do not take up any print positions, so if you include printable
characters within a string, there will probably be an alignment error.
It dawns on me that there might be a printer out there that cannot
print double sized condensed characters (8.55/inch). If you have one
those, the title line (containing the volume label) will probably not
print correctly. If you have this problem, your "SET to double wide
chars" string should be set to a null string (hex "00" in the first
byte), and your "RESET from double wide characters" string should be
set to a string of twelve (12) blanks ("20 20 20 ..."). This will
cause CVR to print the volume label in normal size characters, but the
data will at least be aligned properly. (The LASJET1P.CFG
configuration uses this technique.)
An interesting problem that pops up when programming in "C" is what to
do when you want a character string to actually CONTAIN a byte of zero,
instead of being terminated by one. (Was there any doubt as to the
language I use?) This could create a problem if one of the printer
code strings needs to have a byte of "00"; and sure enough the IBM 5151
printer control code to turn off underlining needs it. My solution is
to turn on the high order bit (using "80" instead of "00") and hope!
While this technique has been tested on some printers, I don't have an
IBM 5151 printer available to test this theory; maybe one of the two
people who do will test it for me? If it doesn't work right, just make
both the "SET to underlined mode" and "RESET from underlined mode"
strings null (put "00" in the first position); this just means that
sub- directory names will not be underlined. I guess anyone still
using an IBM graphics printer probably doesn't use sub-directories,
anyway! (I *REALLY* have to stop being so derogatory!!)
I use this technique to customize the version of the program that I use
personally so that it behaves differently than the way the program is
distributed. I use an Epson LQ-510 printer which supports several
character sets (fonts). By default, the printer will use the "Roman"
character sets, but I would rather have my CVR sheets printed using
"draft" mode. So I have changed my "initialization" string to include
the command to select draft mode (1B 78 80); note that the last byte of
this string should be "00" according to the manual, but the "80" code
works just fine. In all likelihood, most printers will probably ignore
the high bit of a control character, and this technique will work.
***********************************************************************
*************** Log of changes ****************************************
***********************************************************************
1.40 --- 09/08/91
Added the /SORT and /NOSORT options to provide the ability to sort
the file list into alphabetical order.
Changed the separator character between the command switch name and
its value from a colon (:) to an equal sign (=). The correct way to
specify the output printer is:
/PRINT=printer-name
Starting with this version, CVR will perform a complete self-test
every time it is run in an attempt to detect modifications which
might result from infection by a computer virus.
The printer file is now opened before the first diskette is
processed. This means that if there is some condition with the
printer that needs your attention, the messages will appear sooner.
Added some informational messages during processing to show what the
programming is doing as it works. Just to satisfy curiosity.
Made some performance enhancements to the way that diskettes are
read. Diskettes are notoriously slow, so anything has got to help.
CVR will now read the file allocation table (FAT) for the diskette
only when necessary (to process sub-directories on the diskette).
Starting with this version, CVR has a complete license registration
facility, and an attempt has been made to show that I am serious
about the 30 evaluation period. This program represents a lot of
work, and it is well-worth the registration fee.
1.31 --- 08/25/91
Some idiot forgot to test the customization scripts!
So while I was at it, I made CVR more DESQview aware. Normally,
programs that access diskettes play havoc in a DESQview system by
grabbing the CPU and not letting other tasks get dispatched. CVR
is tuned to release the CPU allowing a task switch to occur more
frequently.
1.30 --- 08/25/91
Moved all customization and configuration variables to an external
file. This greatly simplifies customization!
Created an interrupt controlled print driver for parallel printers
to speed processing, especially when running within multi-tasking
environments such as DESQview.
Provided a parameter switch to allow specification of the output
printer.
Note: Starting with this version, the CVR program file is changed to
CVR.EXE (instead of CVR.COM). Users upgrading from a previous
version must delete CVR.COM when installing this release.
1.20 --- 01/01/91
Added a CVR sheet format suitable for 3-1/2 inch diskettes! The
same problem that I used to have with 5-1/4 inch diskettes started
showing up with my 3-1/2 inch ones, so I had to do something about
it!
1.12 --- 12/21/90
Squashed a nasty bug where diskettes using 12 bit FATs having large
sub-directories were not being processed correctly. The bug caused
spurious errors ranging from outlandish garbage being printed to a
complete system lock-up (big red switch time)!
Annihilated an ugly bug which would occasionally cause a random
branch while the program was running under a DOS version prior to
the preferred 4.01. This would normally lead to a complete system
lock-up.
Since these problems were diagnosed on the winter soltice, I feel
completely justified in blaming it on Druids who obviously invaded
and started hacking with my code!
1.11 --- 12/15/90
Corrected programmer's stupidity where running the program with no
disk drive parameter (I always tested using drive B: --- honest! I
swear!!) would issue a warning message about extraneous characters.
1.10 --- 9/1/90
Introduced support for 32 bit FATs, along with the more mundane (12
and 16 bit) varieties. (Now if only I could find a diskette with a
32 bit FAT!) Have you ever wondered what a CVR sheet for a 80 Meg
fixed disk would look like?
1.00 --- a long time ago (in a galaxy far away)
Convert a perfectly good program (written in Pascal) into "C" for no
apparent reason, and decided foolishly to distribute it within the
"shareware" community. What a maroon!